home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2002 November / SGI IRIX Base Documentation 2002 November.iso / usr / share / catman / p_man / cat3n / t_sndrel.z / t_sndrel
Encoding:
Text File  |  2002-10-03  |  6.2 KB  |  133 lines
  1.  
  2.  
  3.  
  4. tttt____ssssnnnnddddrrrreeeellll((((3333NNNN))))                                                      tttt____ssssnnnnddddrrrreeeellll((((3333NNNN))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _tttt______ssss_nnnn_dddd_rrrr_eeee_llll - initiate an orderly release
  10.  
  11. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      _####_iiii_ffff_dddd_eeee_ffff ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE
  13.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_xxxx_tttt_iiii_...._hhhh_>>>>
  14.      _####_eeee_llll_ssss_eeee
  15.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_tttt_iiii_uuuu_ssss_eeee_rrrr_...._hhhh_>>>>
  16.      _####_eeee_nnnn_dddd_iiii_ffff
  17.  
  18.      _iiii_nnnn_tttt _tttt______ssss_nnnn_dddd_rrrr_eeee_llll _((((_iiii_nnnn_tttt _ffff_dddd_))))_;;;;
  19.  
  20. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  21.      This function is used to initiate an orderly release of a transport
  22.      connection and indicates to the transport provider that the transport
  23.      user has no more data to send.  _ffff_dddd identifies the local transport
  24.      endpoint where the connection exists.  After issuing _tttt______ssss_nnnn_dddd_rrrr_eeee_llll, the user
  25.      may not send any more data over the connection.  However, a user may
  26.      continue to receive data if an orderly release indication has not been
  27.      received.
  28.  
  29.      This function is an optional service of the transport provider, and is
  30.      only supported if the transport provider returned service type _TTTT______CCCC_OOOO_TTTT_SSSS______OOOO_RRRR_DDDD
  31.      on _tttt______oooo_pppp_eeee_nnnn or _tttt______gggg_eeee_tttt_iiii_nnnn_ffff_oooo.
  32.  
  33.      If _tttt______ssss_nnnn_dddd_rrrr_eeee_llll is issued from an invalid state, the provider will generate
  34.      an _EEEE_PPPP_RRRR_OOOO_TTTT_OOOO protocol error; however, this error may not occur until a
  35.      subsequent reference to the transport endpoint.
  36.  
  37.      This function resides within both the X/Open compliant _llll_iiii_bbbb_xxxx_nnnn_eeee_tttt and the
  38.      SVR4 compliant _llll_iiii_bbbb_nnnn_ssss_llll Network Services libraries.  Network Services
  39.      applications which require X/Open compliance must link-load with _----_llll_xxxx_nnnn_eeee_tttt.
  40.      Network Services applications which require SVR4 compliance must link-
  41.      load with _----_llll_nnnn_ssss_llll.
  42.  
  43.      On failure, _tttt______eeee_rrrr_rrrr_nnnn_oooo may be set to one of the following:
  44.  
  45.      _TTTT_BBBB_AAAA_DDDD_FFFF               The specified file descriptor does not refer to a
  46.                          transport endpoint.
  47.  
  48.      _TTTT_FFFF_LLLL_OOOO_WWWW               _OOOO______NNNN_DDDD_EEEE_LLLL_AAAA_YYYY or _OOOO______NNNN_OOOO_NNNN_BBBB_LLLL_OOOO_CCCC_KKKK was set, but the flow control
  49.                          mechanism prevented the transport provider from
  50.                          accepting the function at this time.
  51.  
  52.      _TTTT_LLLL_OOOO_OOOO_KKKK               If ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is defined and an asynchronous event
  53.                          has occurred on this transport endpoint which
  54.                          requires immediate attention, then this _tttt______eeee_rrrr_rrrr_nnnn_oooo is
  55.                          passed back.
  56.  
  57.      _TTTT_NNNN_OOOO_TTTT_SSSS_UUUU_PPPP_PPPP_OOOO_RRRR_TTTT         This function is not supported by the underlying
  58.                          transport provider.
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. tttt____ssssnnnnddddrrrreeeellll((((3333NNNN))))                                                      tttt____ssssnnnnddddrrrreeeellll((((3333NNNN))))
  71.  
  72.  
  73.  
  74.      _TTTT_OOOO_UUUU_TTTT_SSSS_TTTT_AAAA_TTTT_EEEE           If ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is defined and _tttt______ssss_nnnn_dddd_rrrr_eeee_llll() is issued
  75.                          in the wrong sequence on the transport endpoint
  76.                          referenced by _ffff_dddd, the _TTTT_OOOO_UUUU_TTTT_SSSS_TTTT_AAAA_TTTT_EEEE error value is
  77.                          returned within the variable _tttt______eeee_rrrr_rrrr_nnnn_oooo.
  78.  
  79.      _TTTT_SSSS_YYYY_SSSS_EEEE_RRRR_RRRR             A system error has occurred during execution of this
  80.                          function.
  81.  
  82. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  83.      _tttt______gggg_eeee_tttt_iiii_nnnn_ffff_oooo(3N), _tttt______oooo_pppp_eeee_nnnn(3N), _tttt______rrrr_cccc_vvvv_rrrr_eeee_llll(3N)
  84.  
  85. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  86.      _tttt______ssss_nnnn_dddd_rrrr_eeee_llll returns 0 on success and -1 on failure and _tttt______eeee_rrrr_rrrr_nnnn_oooo is set to
  87.      indicate the error.
  88.  
  89.  
  90.  
  91.  
  92.  
  93.  
  94.  
  95.  
  96.  
  97.  
  98.  
  99.  
  100.  
  101.  
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.